Skip to main content
TrustRadius
Azure DevOps Server

Azure DevOps Server
Formerly Team Foundation Server

Overview

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

36 people also want pricing

Alternatives Pricing

What is Azure DevOps Services?

Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.

What is CircleCI?

CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…

Return to navigation

Product Details

What is Azure DevOps Server?

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Azure DevOps Server Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.

Reviewers rate Usability highest, with a score of 8.7.

The most common users of Azure DevOps Server are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(280)

Attribute Ratings

Reviews

(1-25 of 30)
Companies can't remove reviews or game the system. Here's why
September 26, 2023

A great product for CI/CD

Anubhav Singhal | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
It is being used for complete ci/cd process, used to create pipelines and manage project with ado board.
  • Continuous integration
  • Continuous development
  • Project management
  • Ease of usage
  • More integration with open source
  • Navigation
It is well suited for creating build pipelines to automate the complete release process and to create testing pipelines. Create and assign different task on ado board. It is also used for code analysis by integrating it with sonar . But it is less user friendly then hira board to mage the scrum and kanban board
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Azure DevOps to manage the end-to-end lifecycle of our code. We use Boards to capture our backlog and manage the work through delivery, Pipelines for our code repository, and Pipelines for CI/CD.
  • Azure Boards is fast to use once you have a good structure in place. You can create or modify each task type quickly. The consequence of that is that is it reduces your admin overhead so its a no-brainer to create lots of smaller tasks.
  • Azure Repos is simple to set up compared to other on prem solutions that we have used. Most options come out of the box including user management.
  • The Pipelines tool is very powerful, and you can quickly create your CI/CD pipelines. Simple to see the state of each pipeline at a glance.
  • Azure Boards can be daunting to set up. There are a lot of different features and if you don't know what you are doing it's easy to overcomplicate things.
  • If you have lots of similar Pipelines to create there is no way to template them, each one has to be created and managed separately. So if your target K8s cluster changes, you have to manually edit each Pipeline.
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Melissa Bryant | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
The firm as a whole makes use of Azure DevOps Server for project management, with its efficient capability to prioritize and approve project needs. Our IT team uses this top-notch application to streamline project management tasks like code versioning and test script administration and to make sure all of our requirements are met through thorough testing.
  • Simple tracking of progress throughout the project.
  • Perform project management duties with superior ability to set priorities and approve work.
  • In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
  • It doesn't work well with tools from other companies.
  • Improvements can be made to the user interface to make it more natural to use.
  • I also think capacity planning may use some fine-tuning.
Integrating with Visual Studio makes it easy to see where things stand in terms of different projects' requirements, and the product is great for prioritizing and approving changes as they come up. An easy-to-use tracking and testing system ensures that all criteria are met, making this a great tool for project managers trying to keep their projects within their allotted parameters.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We work according to Agile methodology and Azure DevOps Server (formerly known as TMS) helps us to track and follow the progress of our work efficiently. We use it for version control as well as to review backlog. As we are more of a Microsoft-based company, it helps us a lot since all Microsoft products can be integrated effortlessly with Azure DevOps Server which enhances user experience.
  • You can integrate it effortlessly with almost all Microsoft products
  • Supports Agile and can be used for version control
  • Bug tracking
  • Ease of use
  • I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
  • The user interface could have been better
  • Agile boards can be better
Scenarios where Azure DevOps Server is well suited: When the other tools you need to use are also Microsoft products bug tracking version control (although GitHub is better) Agile management backlog management scenarios where Azure DevOps Server is not well suited: When you need to integrate services other than Microsoft owned.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Azure DevOps Server is a collaborative project management tool we used in one of our projects while working from home to collaborate among team members, it helped us to track bugs, commit codes, create user story, and various forms of reports related to project. It allows integration with our existing IDEs, version control like Git, setup the CI/CD pipelines for code testing, release and deployments.
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.
  • Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
  • Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
  • Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
  • Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
I work with an agile development team and we use DevOps for capturing and managing user stories and bugs. User stories are categorised into Epics and Features with ease, and it's a very valuable tool for planning and resource management.
  • Resource management
  • Sprint planning
  • Organising requirements
  • Could use a more intuitive interface
  • On-screen demo/tips would be helpful for new users
DevOps is great for managing backlogs, requirements and resources. I don't have enough experience with this sort of software to comment on any downsides, my use is fairly limited but, it's great for my requirements.
Matthew Budram | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
One product to cover the most common engineering activities in tech irrespective of the domain. Whether the team is in medical tech, fintech, aerospace tech, or a business process outsourcing firm, this platform has all the common tools needed in an Agile workspace with extreme collaborations across DevOps, Product, and Engineering. This gives the best centralized toolset, especially if your organization is already a Microsoft-based firm.
  • Version control
  • Requirements definition
  • Secrets library management
  • Continuous integration and deployment
  • Wiki Markdown customization
  • Better Syntax Highlighter in Repository
  • Improvements in Requirements Definition Customization
In my capacity as an architect, the platform gives me the ability to define the architecture within a wiki. I can include details including flow, UML, and ER diagrams in the User Story of Features being defined by the Product Owner, and my engineering team can link the repository pull requests to the story being developed. My Product Owners can now view the business definitions, software architecture, code written, and QA tests performed all on one central platform.
Mark Orlando | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User
Incentivized
We use Azure DevOps to manage and store all our corporate source code and deploy our applications to a string of various environments from development to production. In addition, we use Azure DevOps on a daily basis to manage our agile-based projects. Azure DevOps is used to track and follow the progress of customer support tickets as well. Our business analysts use the Agile Project Management feature to log user stories.
  • Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
  • Our business analysts use its features to document and assign user stories for Agile-based projects.
  • Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
  • For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
  • Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
  • The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
Azure DevOps works great if you spend most of your day in Visual Studio. If you plan on using VS Code, then skip it because Azure DevOps doesn't really work with VS Code. VS Code works with Git. For project management, Azure Dev Ops is okay, but project managers need to provide their team with links to where things are. Additionally, you might be better off using OneNote to document requirements and simply add links to your user stories where developers and testers can read the stories. The Word-like editor in Azure DevOps is extremely primitive.
Ross Borissov | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Azure DevOps in our business unit as an end to end solution for our ALM / SDLC. We have several organizations with various projects, repos and pipelines. We are following Scaled Agile Framework (SAFe) which is well served by Azure DevOps backlog module. We are happy that we could back trace a cloud release through the pipelines back to the work items in the backlog.
  • End to end tracing of released artifacts
  • Scaled Agile Framework implementation with Azure DevOps backlog
  • Versatile and powerful pipelines as code
  • Ability to automatically link automated tests executions to Test Cases
  • A better file editor (like VS code) in the git repo UI
Well suited:
  • Large teams developing heterogeneous applications
  • Following SAFe process / Multiple Agile Release Trains (ARTs) / Portfolio management
  • Company undergoes regular external audits of their SDLC practices
  • Comprehensive reporting is required
  • Pipeline templating is required
  • Many git repositories are needed having to link to a unified backlog
  • Access to backlog work items and reporting is required for business stakeholders
Jeffrey Staw | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
The biggest and best use of Azure DevOps Server (formerly Team Foundation Server) is the gathering and management of user stories for development, coupled with the other elements of information sharing and the metrics it can provide. The ability to track bugs, and the fixes to those bugs, and generally track the evolution of your agile development group is a major plus. While primarily focused on the development organization, Azure DevOps Server (formerly Team Foundation Server) is used by the lines of business by product owners and their associates.
  • User story management
  • Integrations with other products
  • Reporting
  • It does not necessarily play very well with non-Microsoft stacks
  • Upgrades have been cumbersome; however, with the cloud offering, that is mostly off the table as a major issue
  • Some of the search functionality is unclear and difficult to use
  • Could have more pre-built templates; it offers so much it can be challenging at times
If you are a large organization that needs structure, Azure DevOps Server (formerly Team Foundation Server) is a great place to go. It does really benefit from others that have experience with the tool--that is a major plus. Azure DevOps Server (formerly Team Foundation Server) is particularly well suited for organizations that are looking to become more agile in the way they do business, especially in the way they code.
April 14, 2021

Still TFS to Me

Jordan Comstock | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Our dev team uses [Azure DevOps Server] to receive requests for our site from all departments in the company. I have used it as a marketing user. It is being used across the entire organization. It helps to address the business problem of prioritizing the work that we need to be done on our website.
  • Orginazation
  • Notifications
  • Complex nesting of projects
  • So many options, getting the team on the same page
  • Formatting
  • Tricky for new users
We still call it TFS. It is very useful for our marketing team and working with our developers. Every time we have a page, a bug, a user story, or an epic project, we can put the details into [Azure DevOps Server] and work back and forth with our dev team in there to complete the work.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
TFS is used for ALM of all in house supportive software, development of our flagship product and clinical studies for our latest version. TFS acts as a central hub for requirements, code, tests and reports. It links these facets of the product life cycle together.
  • Linking together all aspects of the application life cycle, from requirements to code to builds and test.
  • Trace-ability of all application life cycle via reports and queries.
  • Automated testing.
  • Flexibility of source code management. Centralized or distributed.
  • Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
  • Capacity planning could be improved.
  • Dot Net framework 260 character path limit is ridiculous.
Team Foundation Server (TFS) is best for large scale enterprise deployments. Not needed for a small company. With the infrastructure investment, TFS can aid large scale software development immensely. TFS is highly customizable, but if you go the route of heavy customization, don't upgrade to the latest version aggressively. Plan to invest in at least one full time TFS administrator. Make sure the users are properly trained.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Azure DevOps Server is being used across the organization as a defect/bug tracking system for IT projects similar to Jira. The business problems it addresses are mainly related to issue tracking and traceability. There is a multitude of IT deployments at our company, and hence, lots of QA/UAT testing. When defects are captured during these phases, they are logged in Azure DevOps Server and tracked.
  • Organization
  • Defect tracking
  • Severity
  • Escalation
  • Issue/user traceability
  • Easier interface.
  • Less drop downs and tabs.
  • Email notifications.
The best use for Azure DevOps Server is for issue tracking and reconciliation for defects during the QA process.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
I am currently using Azure DevOps Server with a client on a scrum project to build a business application. In the company, Azure DevOps Server is mostly used by our specific project but does have other users and different projects. It helps manage the scrum process and provides organization and clarity to a project with many moving parts and members.
  • Organization of tasks per team member
  • Statistics provider for data related to capacity and output
  • Good UX/UI experience for clarity
  • Copy/Paste functionality could be improved
  • Ability to see all team members more clear visually
  • Sort feature on columns could be better
Azure DevOps Server is a great tool for keeping large projects organized. It is well suited for building large, business applications that require a lot of organization and history of the project that is accessible.
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.
Brendan McKenna | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use the Azure Dev Ops server throughout the IT department of our organization. It is utilized by Business Analysts, Scrum Masters, Developers, and QA. We have Git integration enabled and it has been an awesome experience with its integration to our source code. I especially love the built-in ability in the latest version to perform source code wide string searches. This makes it exceptionally easy to find code references and delve into new areas quickly. Aside from source control, it is our UI interface for all of our SCRUM project management needs. We create all of our tasks on the work items board and it makes it easy to see the progress of the overall team. Overall it's just been a great experience and I can't think of any complaints.
  • Git integration has been fantastic.
  • Provides a convenient UI for managing the SCRUM process.
  • Built-in Code Review feature and completion policies.
  • I wish I could default to a specific dashboard on load.
Great for source control, project management, and code reviews. It is really critical to put in place code review policies with required reviewers before a pull request can ever be merged into a target branch. As a senior developer sometimes I feel this can be cumbersome but there have been a few instances where I have caught a major error in a pull request and was able to prevent the code from being merged.
Vaibhav Choksi | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Dell Technologies uses Team Foundation Server for managing multiple projects across the North America region and rolling out in all other regions. If you use Visual Studio for development, TFS, or its online equivalent VSTS, you can have a fairly seamless end-to-end integration. Out of the box, it provides code management, testing, work hierarchy in agile formats, automated build, and deployment.

Dell manages source code, project reporting, engineering progress tracking and release management for agile software development. Microsoft TFS is also leveraged by the Product Management group to define and manage product requirements and managing the technical backlog. TFS really makes it easier to perform an end-to-end integration, reporting, tracking, code management, automated build, and deployment, etc.
  • TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
  • It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
  • It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
  • TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
  • Development in branches is hard to achieve and TFS has a room for improvement.
  • Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
Team Foundation Server is well suited in product management
  • Easier to build a technical backlog.
  • Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
  • Make a Product Manger's and engineering teams' life easier in meeting and tracking.
  • Project managers can easily track the work and create reporting.
Vinicius Lima | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server in the Information Systems Department in our company. All developers have access to Team Foundation Server to do code versioning. We use it integrated with Visual Studio to check-in and check-out our projects' code. We also use the web interface to navigate between code versions and to manually download code when necessary.
  • Integration with Microsoft products, like SharePoint, IIS, Visual Studio
  • Users are able to access via desktop client, web browser and through Visual Studio
  • Code version control
  • Bad UX and UI in the web interface
  • Merging code is a very hard task
  • Development in branches is also hard to achieve
  • Not so easy to upgrade server version
TFS is well suited to developers and teams that work with Microsoft technologies and products. For other scenarios, alternatives like Git can deliver more powerful and reliable features. Also, developing software in branches is very difficult, as well as merging code. These tasks needs to be carefully planned to avoid broken code and headaches in your company.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are currently managing a large project and we use TFS to manage bugs, code and releases. It is only being used by the technical team but others are coordinating with us to make sure their bugs make it into the system. As well, we are using data from the system to routinely give updates to management on the status of the project as well as any concerns or risks.
  • The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
  • Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
  • Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.
  • Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
  • Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
  • Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.
TFS is very good when working on a large project with a lot of moving pieces. When you have many BAs involved and a lot of user stories, it can be extremely useful to consolidate information. If you are not working on a large project with many users and developers, it may be excessive. However, in general, the tool is extremely helpful when implemented correctly.
Markus Hopfenspirger | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server as Source Control Managment System and for automated Builds and Tests. We don't use the WorkItem System of Team Foundation Server. We Used it a couple of years ago, but it was to complicated. Right now we just use Trello with a Scrum AddOn for Task and Backlog Planning. Right now only our Developers are using Team Foundation Server.
  • I like the Team Foundation Source Control Management much more compared to other Systems like GIT, because:
  • - Perfect Integration into Visual Studio
  • - Easy and direct checkout/check-in
  • - Perfect branching and merging
  • - Workflow Support with autmated Reminders
  • The Build System is just great. Since Version 2017 its very easy to integrate self made tools into the build process.
  • Easy Managament of Users and User Rights.
  • Team Foundation Server could be improved in the Task and Backlog Managment for smaller Teams. E.G.: It's hard to quickly write down Tasks during a meeting because you have to fill in lots of Fields per WorkItem. It is hard to push the Items around.
Well, as said before. I like TFS for Source Control and automated Builds and Testing, but it could be improved in the area of Task Management.
Score 6 out of 10
Vetted Review
Verified User
Incentivized
We used TFS in conjunction with a SharePoint upgrade to roll out Agile/Scrum. The key thing was traceability between MS products (linking). There were multiple project teams and a scrum of scrums was used. Adoption rate was decent, but it was tough to cut the cord on share folders.
  • Traceability between MS Suite
  • Clear what's a Bug, User Story, Feature, Epic
  • Linking test cases
  • Bad use of real estate is it's No. 1 failing, why all the white space?
  • Too much functionality makes it difficult for new users to jump onboard - it's daunting at first
  • Configuring dashboards is easy, but not necessarily what you want to show to upper management - needs some tweaking
If you're JUST doing project management, you probably don't need it - too powerful. If you're doing code and development, it's more useful than something that is basically just an issue tracker/kanban board/wiki.
Rich Mephan | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Team Foundation Server (TFS) is used by the development and test teams at Peppermint Technology. It is used for management of our source code and we also take advantage of the automated build functionality. We also use it for storing all of our release user stories, tracking enhancements and bugs as well as taking advantage of the project management tools to support our agile development process.
  • Work Item tracking - The ability to define the flow of your work items to match your development/test process is really valuable
  • Version Control - The ability to easily track changes between every checked in version of source code can be a life saver
  • Project Management - The project management dashboards showing things like burndown enables us to easily track whether we are on target for a release
  • Integration between our help desk system and TFS was possible but not as easy as I would expect considering both are Microsoft products
  • Advanced reporting for dashboards could be made easier
TFS is a really good tool for managing small to medium-sized development teams. The ability to customize it to suit your own processes means it should be suitable for any business, though I have to confess I do not have any experience of using it within a large enterprise sized development team split across disparate locations.That said we do have developers spread across the UK and they manage to work remotely with no problems at all.
October 26, 2017

Is TFS the right tool?

Erik Sheafer | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We are using TFS in our software division as a source control for code and DB objects. It allows us most importantly to keep a history of our code. Secondly, we can do deploys from this environment out to our many environments.
  • TFS has an excellent interactive UI for all users to make source control easy to use.
  • TFS has the backing of a major company, Microsoft. Updates and the way it is used gets regular updates.
  • TFS integrates into Visual Studio.
  • TFS has many tools for many different areas in the development life cycle.
  • There is no real ability to work offline. You need to be actively connected to it in order to see history.
  • Having many hands in the same project/file can cause conflicts that can be hard to resolve.
  • having a "master" branch is difficult in TFS, it can be done but it is slow and cumbersome and not an intuitive process.
I think if you work in a Microsoft exclusive environment, this is the tool for you. If you are in an arena where you might have C#, Java, or Python other tools might be better suited to your needs. TFS can be very costly but if it is instituted correctly with RM tools, it can be a wonderful thing. If you are a small shop use a free source control.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Team Foundation Server (TFS) to track the development and delivery of tools we implement across business units.
  • Automatic generation of burn down chart
  • Easy to link user stories and tasks across
  • Easy to move tasks across user stories
  • Easy to move user stories across sprints
  • There are issues encountered when uploading more than one attachment to a task. One needs to refresh first then save.
  • The Admin function where you add iterations isn’t very user-friendly.
It works best with multi-located teams working on an Agile project.
April 13, 2017

TFS = meh

Score 5 out of 10
Vetted Review
Verified User
Incentivized
We use team foundation server for source control.
  • Project management
  • Scrum
  • Integration with visual studio
  • Not a user friendly implementation of Git
  • TFS version control is not widely used in favor of Git
Using visual studio to manage source code instead of GitHub out bitbucket
Marcus Felling | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Team Foundation Server (TFS) is used as an Application Management Lifecycle suite by PMO, Software Development, and Information Technology. TFS ensures that software initiatives drive overall business value.
  • Work Item management.
  • Build automation - enables Continuous Integration out of the box, cross-platform, easy to use.
  • Code repositories - Hosts Git and TFVC repositories, provides excellent pull request experience for Git users.
  • RESTful API - Provides the ability to script/automate just about anything.
  • Visual Studio Team Services just about solves all of the criticisms I had of TFS.
  • Release Management is overly complicated and changes constantly, hard to keep up. I use Octopus Deploy as an alternative.
TFS is especially well suited for .Net shops if they already have MSDN subscriptions; in that case it's pretty much free and a great all in one ALM suite. TFS now supports development of any tech stack, so it should also be evaluated by teams doing more than just .Net development.
Return to navigation